5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

LOCAL


A new LOCAL statement allows fields to be declared to be LOCAL to the current context.

LOCAL saves the named field's value. When the current context completes, it restores the saved value before returning to the invoking context.

LOCAL works in subroutines called via a GOSUB, and in Start of Process event points.

Description:

A LOCAL statement is (nearly) equivalent to a RECEIVE statement that executes without a matching PASS statement (such a RECEIVE statement will set the next T/F to F, but a LOCAL statement doesn't change the T/F flags).

When you execute a LOCAL (or RECEIVE) statement, the engine decides the point in time that the original value should be restored according to the following rules:

1) If you execute a LOCAL (or RECEIVE) while there is a GOSUB active (in the current event point), the original value is restored when you execute a RETURN statement.

2) If there is no GOSUB active, the original value is restored when the event point ends (with one exception described in the next rule).  That means that you can add LOCAL statements to the beginning of an event point to protect variables that you want to use in that event point.

3) If you execute a LOCAL statement (and there is no active GOSUB) in the Start of Process event point, you are protecting a variable for the life of the process (the original value is restored when the process ends).

Application Design Manual                                         "Powered by Appx Software"

660

©2006 By APPX Software, Inc. All Rights Reserved